AVEVA™ Application Server 2020 R2 Readme

Issue Number

Related Issues

Description

CR L00150650

SR 59010331: The NmxSvc service was not able to communicate with remote platforms and appeared hung, even though the binding order appeared to be correct.

CR L00154357

SR 103161805; SR 103161861: ShowSymbol action, in either an animation or a script, did not function within an Industrial Graphic embedded in any native or third-party AVEVA OMI app.

CR L00155863

SR 103164207: When an InTouch HMI run-time node was restarted, it resulted in both the WinPlatform and AppEngine crashing. Both would then have to be restarted manually from Platform Manager.

CR L00156334

SR 103165479: After upgrading from System Platform Update 3 to Update 3 SP1, AVEVA OMI ViewApps would sometimes fail to launch, and an accompanying warning related to the ViewApp navigation model was logged.

CR L00156473

SR 103166596: After a user entered their credentials and logged in to an AVEVA OMI ViewApp, User Logon popup closed, but any panes that were populated by using a ShowContent script were then hidden.

CR L00156633

SR 73610144: A button triggering a script to change a custom property value in an embedded symbol did not update the value of a custom property i n the container graphic, as the script was designed to do. Instead, a message was logged.

CR L00156802

SR 63212608: Using redundant AppEngines in Application Server 2017 Update 3 SP1 resulted in issues reading attribute values correctly.

CR L00156825

SR 103166683: The source topic items sent via MQTT had a different syntax than the topic items received by the OI Gateway; all letters were capitalized on the OI Gateway, while MQTT is case-sensitive).

CR L00156834

SR 63810143: Not all communications quality codes were transferred from the AVEVA Telemetry Server to Application Server; only good (192) and bad (0) quality codes were sent.

CR L00156841

SR 22210557: The addition of new users to a Galaxy (security enabled) was not propagated to client nodes.

CR L00156998

SR 103167805: In System Platform 2017 Update 3 SP1, when objects containing duplicated friendly names/aliases were imported into a galaxy, the import did not succeed and a message, "Unable to update the friendly name during import" was logged.

CR L00157041

SR 103168029: Attempting to backup a Galaxy with GRAccess when the logged-in user belongs to the aaConfigTools group but not Administrators did not succeed, and an error, "cmdNoSuchGRNode "Operation failed because the given GR Node is invalid"" was logged.

CR L00157107

SR 103167824: The MapApp did not start at run time. This was caused by an inability to start the HTML5 graphics web server.

CR L00157206

SR 103168446: When the ShowGraphic() script function was used to open an Industrial Graphic in an AVEVA OMI ViewApp, the graphic opened with a thin blue border.

CR L00157256

SR 103168239: The SendKeys() script function generates a "File Not Found" exception when executed from an Industrial Graphic.

CR L00157305

SR 103169185: When a gradient color was used, the gradient rendered differently at run time in an AVEVAvOMI ViewApp than it appeared during development. The gradient rendered correctly in both WindowMaker and WindowViewer.

CR L00157330

SR 103167351: Redundant platforms did not failover, and if a deployed platform was stopped, it became unavailable and could not be restarted.

CR L00157396

SR 103168721: When the ShowGraphic() script function was used with a layout name configured as the GraphicName property, it did not open the layout as a modeless window.

CR L00157417

SR 40711173: Show Halo remained visible around a Hotlink for a prior graphic, even after the symbol was no longer being displayed.

CR L00157420

SR 40711172: In an AVEVA OMI Application copied to a node without a System Platform product installed, navigation worked but action was delayed.

CR L00157533

SR 22210576: Nodes in a network configured with a DHCP server were sometimes assigned a partial IP address through the NMXService, even though they had not yet received an address from the DHCP server.

CR L00157567

SR 78610061: After an embedded graphics was deleted from a container graphic, references to the deleted graphic still remained. The references also remained if the owning object was imported.

CR L00157581

SR 24910499: Errors were logged when migrating a galaxy from version 2014 R2 SP1 to 2017 Update 3 SP1, and not all objects were migrated successfully.

CR L00157669

SR 51316633: After upgrading from System Platform 2014 to System Platform 2017 and later, scripts that used "==" for string comparison were no longer valid when used with dynamic arrays. (However, the StringCompare() method did work.)

CR L00157708

SR 103169334: When using a template with an object wizard and a linked symbol that contains scripts referencing an embedded symbol within the linked symbol, warnings were logged that references from the embedded symbol were missing.

CR L00157731

SR 12615055: While navigating the asset hierarchy using the BreadCrumb App or NavTree app, a warning that the "Hierarchy item for the given hierarchy path "XXXXX" is not found," and it was not possible to navigate the application.

CR L00157876

SR 101364576: Random engine crashes were occurring, and message indicating an NmxCallback->DataReceived to local engine failed with error 0x800706be.

CR L00157978

In Flex license mode, clicking on the Refresh button in License Status View and deploying a platform resulted in deployment failure, and the message “Unable to deploy the platform as requested license is not available” message and deployment failure was displayed. The same issue occurred when changes were made to the platform and the platform was redeployed.

CR L00158019

SR 78610069: After failover, the InvertValue of an attribute was set to true, and thus, did no longer reflected the correct attribute configuration.

CR L00158022

SR 103167644: After migrating an InTouch HMI application from version 2014 to 2017 Update 3 SP1, issues with ArchestrA objects not working were noted occasionally after the application was deployed, and errors appeared in the logger.

CR L00158104

SR 57211661; SR 76410095: An attribute configured as write-only on a Redundant IO object could not be written to and displayed a configuration error. If the attribute was configured as read/write, the attribute worked correctly.

CR L00158110

SR 22111604: None of the data within a level 1 graphic was displayed until a data change was received from an OPC Client data source.

CR L00158130

SR 103170046: A symbol was corrupted when it was linked to from a template, which resulted in an the symbol showing as empty within the template. When an attempt was made to remove the symbol, the IDE stopped working and closed.

CR L00158159

While converting Field Attributes in MRO Galaxies, errors were logged from the IOMBLS service and the aaGR process restarted during the attribute conversion.

CR L00158169

SR 37613361; SR 37613354: While importing objects, and with multiple users connected to the IDE, the IDE stopped working and an error was logged that communication to the target machine failed.

CR L00158291

Scripting failed when ".ToString()" was used on embedded level custom property

CR L00158294

SR 103168167: The IDE had slow response to operations such as opening editors and platform configuration.

CR L00158312

SR 103169965: With Alarms and Events storing via Historian blocks, the alarm messages in History often stored the wrong value.

CR L00158322

CR L00159672

SR 103173644: Some animations that should have shown the tagname showed the object name instead.

CR L00158397

SR 103171234: There is was an offset when using Hindi characters that resulted in misalignment between text objects and textbox objects.

CR L00158454

SR 76410440: When a new asset was configured on System Platform 2020 (Chinese version and Chinese OS), and the instance name included Chinese characters, the asset did not appear when the ViewApp was in preview mode.

CR L00158455

SR 103170875: When the "Is Visible" property of each divider was unchecked in a layout with two or more panes, and a symbol was then added to each pane, the dividers were still displayed when the ViewApp was previewed.

CR L00158558

SR 103171557: Popup windows in AVEVA OMI ViewApps showed unwanted borders to the sides of the popups using either the the "ShowSymbol" animation or the ShowGraphic script function.

CR L00158568

Checking in a template with embedded graphics took much longer in System Platform 2020 compared to performing the same operation in System Platform 2014.

CR L00158576

After a fill was added to AlarmBorder in the Galaxy Style library, a ViewApp stopped responding and then crashed when the NavTree app was opened, and exceptions related to AlarmBorder were observed.

CR L00158650

CR L00158691

SR 103172044; SR 103172516: When a customer-developed app that included properties such as Value Min and Value Max was imported to into System Platform 2020, the app properties no longer worked as expected.

CR L00158683

SR 103170836: After two HotFixes were applied (L00155899, L0015710), setting the start datetime to midnight in the AVEVA OMI TrendPen (00:00) and duration to 1440 min (24 hrs), resulted in the end time as 22:00 instead of 0:00.

CR L00158685

SR 103171917: Single AppEngine Flex License did not function correctly when using redundant engines.

CR L00158786

SR 103172593: The Combo Box control SelectedIndex property did not work correctly in an AVEVA OMI application, even though it worked correctly in an InTouch HMI application.

CR L00158970

After Field Attribute conversion, the 'Alarm for attributes' fields for some state alarms were not populated via 'Me.<Attribute name>' relative reference.

CR L00159105

SR 103172709: On Secured Write popups in AVEVA OMI run time, the relative name "Me." was shown instead of the object name.

CR L00159150

SR 56910113: In System Platform 2017 Update 3 SP1, IO device mapping was not able to list more than 500 IO instances.

CR L00159152

SR 76610219: During failover, some objects were quarantined and errors and warnings were logged.

CR L00159169

When Field Attribute conversion was done on a galaxy migrated from System Platform 2014 P01 to System Platform 2020, the conversion of some objects failed, and import of those object into a new galaxy also failed.

CR L00159289

SR 63512116: In the AVEVA OMI NavigationApp NavBreadcrumbControl, font changes made in the editor did not take effect in the ViewApp at run time.

CR L00159399

SR 63810209: When the "Navigate on double-click" property in the AVEVA OMI AlarmApp was enabled, navigation to hidden objects that had alarms did not work. Hidden objects have an alias name starting with the underscore character, but navigation to the alarming objects by double-clicking on the alarm should have worked.

CR L00159489

SR 103172189: Intermittently, the error "Binding cannot be changed after it has been used" was logged when a ViewApp was opened.

CR L00159584

SR 103174367: New galaxy database files were created using the C:\ drive as the path, instead of a custom default path that had been defined for database files.

CR L00159622

SR 48913081: Migrating a galaxy from System Platform 2017 U3 SP1 to System Platform2020 resulted in many objects going into warning state.

CR L00159815

SR 56910119: Combo box exhibited inconsistent behavior, and did not show the default selected after the item was changed with clear()/additem.

CR L00159923

The AVEVA OMI AlarmApp was unable to resolve a custom query configured as "In" that used the MyViewApp system namespace (for example, MyViewApp.Navigation.CurrentAsset). A warning was displayed in the ViewApp when validating the query.

CR L00159957

It was not possible to move a template to security group other than the Default group in System Platform 2020. This could be done in System Platform P2017 U3 SP1.

CR L00160058

SR 960003702: When the script function StringFromGMTTimeToLocal() was called from InTouch HMI and from an Industrial Graphic, it did not work the same way and showed different results.

IMS 511494

SR 0001815136: Scripts using BindTo did not work with the AlarmMode attribute in an AVEVA OMI ViewApp. Instead of seeing the expected value ("Enable", "Disable" or "Silence"), the string "ArchestrA.Visualization.Services.RuntimeData.RuntimeDataSupport.CustomEnum" was shown.

IMS 517491

SR 25315475: Connection issues were experienced with RDI objects, where the DI source remained disconnected or unknown.

IMS 553941

A float attribute on a UserDefined object would sometimes display the value as an integer, with no decimal values, instead of a float. The attribute connected to an OPC server via an OPCClient object.

IMS 562170

When a platform was deployed, it could not be set OnScan due to failure in xxSecurity.

Issue Number

Description

TFS 624132

On some monitors, the System Platform IDE shortcut menus are displayed partially off-screen, making them difficult to read or make a selection.

Workaround: This workaround is documented on a Microsoft Community forum and is summarized below: (see
https://answers.microsoft.com/en-us/windows/forum/windows_7-desktop/context-menu-going-left-not-right/a09e42df-fdd0-45fc-a501-7e5e145a22b3?auth=1)

Note: This workaround is applicable to all supported Windows and Windows Server operating systems.

1. Press the Windows logo key+R to bring up the Run dialog box.

1. In the Open line, copy and paste the following text:
2. shell:::{80F3F1D5-FECA-45F3-BC32-752C152E456E}
3. Click OK.
4. This starts the Tablet PC Settings configuration dialog, even if you are not working on a Tablet PC.
5. Select the Other tab.
6. In the Handedness section, select the Left Handed option.
7. Click OK.

TFS 785665

Under certain circumstances, when migrating a CAB file from an older galaxy that contains Industrial Graphics and utilizes the Historical Trend control to System Platform 2017, the migration may stall at some point and fail to complete. No error message will be displayed.

Workarounds: The workaround varies, depending on the System Platform version that you are migrating to System Platform 2017:

Migrating from System Platform 2014 or System Platform 2014 P01:

Copy the following HistorianClient-2014 binaries from C:\Program Files (x86)\ Common Files\ArchestrA to
C:\Program Files (x86)\ArchestrA\Framework\bin.

Note: If the same computer is upgraded to System Platform 2017, the 2014 binaries can be taken from the System Platform 2014 installation CD.

• aaHistClientDatabase.dll
• aaAFCommonTypes.dll
• aaHistClientUtil.dll

Migrating from System Platform 2014 R2:

1. Install System Platform 2014 R2.
2. Re-create the backup of the galaxy.
3. Migrate the CAB file created in step 2 to System Platform 2017.

Migrating from System Platform 2014 R2 P01 or System Platform 2014 R2 SP1:

You can directly migrate these CAB files to System Platform 2017. No intermediate steps or actions are needed.

Migrating through intermediate versions to System Platform 2017: If you migrate CAB file to a version lower than System Platform 2017, and then migrate the CAB file to System Platform 2017, you must re-import the Historian Client controls in the intermediate version, before you migrate the CAB file to System Platform 2017. See the following two examples:

Example 1: CAB file migration path: 2014 or 2014 P01 > 2014 R2 > 2017:

1. After migrating the CAB file to 2014 R2, re-import the Historian Controls into Application Server 2014 R2.
2. Install 2014 P01.
3. Back up the galaxy.
4. Migrate the CAB file to System Platform 2017.

Example 2: CAB file migration path: 2014 R2 > 2014 R2 SP1 > 2017:

1. After migrating the CAB file to System Platform 2014 R2 SP1 , re-import the Historian Controls into Application Server 2014 R2 SP1.
2. Back up the galaxy.

Migrate the CAB file to System Platform 2017.

TFS 794197

While installing the Application Object Toolkit (AOT), under certain conditions during the “Updating the system” step, the following error may be displayed by Visual Studio:

“The Add-in ‘AOT Editor’ failed to load or caused an exception. Error number: 80131604.”

Workaround:

1. Add the following entry to the "devenv.exe.config" file:

   <dependentAssembly>

   <assemblyIdentity name="ObjectDesignServer2" publicKeyToken="23106a86e706d0ae" culture="neutral" />

   <bindingRedirect oldVersion="6.0.0.0" newVersion="7.0.0.0" />

   </dependentAssembly>

2. Uninstall and re-install the Application Object Toolkit (AOT).
3. Once re-installation of the AOT is complete, create a new file named "ABuilderCmd.exe.config" in the folder <AOT install path>\bin.
4. Add the following content to the new file:

   <?xml version ="1.0"?>

   <configuration>

   <runtime>

   <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">

   <dependentAssembly>

   <assemblyIdentity name="ObjectDesignServer2" publicKeyToken="23106a86e706d0ae" culture="neutral" />

   <bindingRedirect oldVersion="6.0.0.0" newVersion="7.0.0.0" />

   </dependentAssembly>

   </assemblyBinding >

   </runtime>

   </configuration

TFS 922856

The object name extension "_New" cannot be used if another object in the Galaxy uses the same name without the "_New" extension. For example, if you have an object named "Pump," you cannot have a second object named "Pump_New." You could, however, use "Pump_Old" and "Pump_New." Note that this restriction applies to templates as well as instances. For example, you cannot have a derived template named "$Area_New" or "$ViewApp_New" since these add the "_New" extension to a base template name.

TFS 1260610

When defining a custom checkpoint directory path in the platform object, and using C$ in the file path name, warnings can appear in the logger when performing a stage-deploy operation to a remote node, even though the deploy is successful. This issue is related to File Sharing Support in Windows Server 2012 R2 and the warnings are related to being unable to create the checkpoint directory.

Workaround: Follow these recommendations to avoid issues with creating the checkpoint directory.

• Do not use C$ to define a customized checkpoint directory path.
• Create a folder, share it as read/write with the ArchestrA User (also called the ArchestrA Network Account) and use this as your customized checkpoint directory. Then perform the stage-deploy to the customized directory.

TFS 1273489

Similar to default Windows behavior, the hot key for menu items in the IDE menu bar may not be displayed. For example, the hot key "E" in the Edit menu item will not be underlined. However, once you press the <ALT> key, the menu hot keys will appear and will remain underlined until you execute a command, which is the same as default windows behavior.